Opening a game via Provider URL

Evenbet now supports an alternative method for launching games — using a URL received from the game provider via API. In addition to the existing method, where the game launch URL is generated internally, this new option allows integration with external provider links. To enable it, contact the Evenbet team.

---

How to Get the Provider URL

1. Evenbet sends a POST request to the provider’s endpoint with a set of required parameters (see below). The POST request sent to the provider must include an Authorization header to ensure request security. This header is required and should contain the token used for authentication, as described in the documentation: Integration of external casino providers to Evenbet.
2. The provider validates the request and returns a JSON response:
   • if valid, it includes the launch URL;
   • if invalid, it returns an error with a code and message.
3. Evenbet uses the received URL to launch the game.
4. The provider proceeds with the login callback flow, as described in the Main system callbacks documentation.

---

Parameters for Real Game

The POST request

Parameter	Description	Mandatory	Type
token	A temporary token with a short lifespan (default: 60 seconds) used for requests to the system's login method.	+	string
gameId	Game ID	+	string
mode	Real/demo game (0 for real mode, 1 for fun mode)	+	integer
language	Session’s language parameter, written as two-letter codes based on the ISO 639-1 standard (e.g., en for English)	+	string
platform	Desktop, mobile	+	string
currency	Session’s currency	+	string
userId	User ID in the Evenbet system	+	integer
userIp	Player’s IP address	+	string
balance	Current user’s balance	+	float
country	User’s country code (ISO), if provided	-	string
casinoId	Casino operator ID (is sent at the provider's request)	-	string
lobbyUrl	Game lobby URL (is sent at the provider's request)	-	string
currencyPrecision	Currency decimal precision	-	integer

It is also possible to send any additional parameters with fixed values required by the provider.

Example of the request body:

{
  "token": "c38d*******************************", 
  "gameId": "20803", 
  "mode": 0, 
  "language": "en", 
  "platform": "desktop", 
  "currency": "USD", 
  "userId": 42, 
  "customParam": "customValue", 
  "userIp": "95.216.239.252", 
  "balance": 82936, 
  "country": "FI" 
}

---

Parameters for Fun Game (demo mode)

The POST request

Parameter	Description	Mandatory	Type
gameId	Game ID	+	string
mode	Real/demo game (0 for real mode, 1 for fun mode)	+	integer
platform	Desktop, mobile	+	string
language	Session’s language parameter, written as two-letter codes based on the ISO 639-1 standard (e.g., en for English)	+	string
currency	Session’s currency	-	string
userIp	Player’s IP address	-	string
casinoId	Casino operator ID (is sent at the provider's request)	-	string
lobbyUrl	Game lobby URL (is sent at the provider's request)	-	string

It is also possible to send any additional parameters with fixed values required by the provider.

Example of the request body:

{
  "gameId": "29005", 
  "mode": 1, 
  "language": "en", 
  "platform": "desktop", 
  "currency": "USD", 
  "customParam": "customValue", 
  "userIp": "95.216.239.252" 
}

---

Response Format

Example of a successful response (with launch URL):

{
  "url": "game_launch_url" 
}

Example of a failed response:

{
 "error": { 
   "code": 2, 
    "message": "Error Code 2, ask server's administrator for help" 
  } 
}